Release 10.1A: OpenEdge Development:
Messaging and ESB

requestReply procedure

Sends a message to a destination specified in the JMSReplyTo message header field and designates the messageConsumer parameter for processing replies.

Syntax

PROCEDURE requestReply. DEFINE INPUT PARAMETER destination AS CHARACTER. DEFINE INPUT PARAMETER message AS HANDLE. DEFINE INPUT PARAMETER replySelector AS CHARACTER.      /*UNKNOWN means                                                      receiving all replies*/ DEFINE INPUT PARAMETER messageConsumer AS HANDLE.  /*UNKNOWN is illegal*/ DEFINE INPUT PARAMETER priority AS INTEGER.            /*Session default is                                                      used if UNKNOWN./* DEFINE INPUT PARAMETER timeToLive AS DECIMAL.      /*Session default is                                                      used if UNKNOWN./* DEFINE INPUT PARAMETER deliveryMode AS CHARACTER.       /*Session default is                                                      used if UNKNOWN./*

Applies to

Session objects

Notes

The term destination is used for both topics and queues.
The 4GL-JMS implementation automates the request/reply sequence:
Sending a reply by setting the reply OUTPUT parameter of the message handler.
Requesting a reply by calling the requestReply procedure with a reply Message Consumer.
The 4GL-JMS implementation uses a temporary destination for the reply. It is an error to set the JMSReplyTo field of the message explicitly if requestReply is used. The reply is received by messageConsumer asynchronously, just like any other message reception. The temporary destination is deleted when the Message Consumer object is deleted.
This procedure executes remotely (sends a message to the OpenEdge Adapter for SonicMQ).

See also

For more information, see the "Request/Reply" section.